docs: a2a webhook payload structure and url routing best practices #280
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
youbek
commented
Dec 10, 2025
youbek
commented
Dec 10, 2025
youbek
commented
Dec 10, 2025
bokelley
reviewed
Dec 11, 2025
bokelley
approved these changes
Dec 11, 2025
…eration id to the url routing - Clarify that completed/failed statuses use Task object with data in .artifacts - Clarify that interim statuses (working, input-required) use TaskStatusUpdateEvent with data in status.message.parts - Add best practice guidance for URL-based routing (task_type and operation_id in URL) - Deprecate task_type and operation_id fields in webhook payload (backward compatible) - Update webhook handler examples to use URL parameters - Consistent guidance across both MCP and A2A protocols
youbek
force-pushed
the
fix/a2a-webhook-payload-structure
branch
from
2f28d80 to
a4c4e2e
Compare
youbek
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is follow up to the push notification refactoring PR. Turns out I had missed couple of important documentation mistakes that I've found once i started the implementation.
Specifically ads clarification: